The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 21, 2026 11:59pm

PR Summary

High Risk
High risk because it removes the existing HubSpot webhook provider/trigger surface and introduces a new polling pipeline with cursoring/idempotency that directly affects workflow execution reliability and HubSpot API usage.

Overview
HubSpot triggers are consolidated and re-implemented as polling. The docs and HubSpot block config are updated to replace 27 manual webhook triggers with a single hubspot_poller trigger, changing trigger configuration from app keys/curl setup to an OAuth credential plus object/event selection and filters.

Adds new HubSpot polling implementation and selector endpoints. Introduces a hubspot polling provider (lib/webhooks/polling/hubspot.ts) with monotonic (timestamp, objectId) cursoring, optional property-change detection, and list-membership polling, registers HubSpot as a polling provider, and adds new OAuth-backed selector APIs/contracts (/api/tools/hubspot/{properties,lists,pipelines,owners}) used for trigger UI dropdown/autocomplete. The legacy HubSpot webhook provider handler and related trigger mocks/configs are removed.

^{Reviewed by Cursor Bugbot for commit 324741d. Configure here.}

Greptile Summary

This PR replaces 27 individual HubSpot webhook trigger configurations with a single OAuth-native polling trigger (hubspot_poller) that fetches changes via HubSpot's CRM Search API every minute using each user's OAuth token.

• Core polling engine (lib/webhooks/polling/hubspot.ts): strict monotonic (timestamp, hs_object_id) cursor with a cursorFrozen gate on the first failure; supports contacts/companies/deals/tickets/custom objects plus a separate list-membership code path; per-record property_changed snapshot diff with LRU-bounded GC.
• New UI trigger (triggers/hubspot/poller.ts): live dropdowns for properties, lists, pipelines, stages, and owners; getScopesForService('hubspot') injects required CRM scopes into the OAuth grant.
• Four new selector API routes (/api/tools/hubspot/{properties,lists,pipelines,owners}): standard authorizeCredentialUse + refreshAccessTokenIfNeeded pattern, registered in the contracts index.

Confidence Score: 5/5

Safe to merge — the polling core is well-designed, the cursor and failure-recovery logic are correct, and all four new API routes follow the established auth pattern.

The (timestamp, id) cursor with cursorFrozen failure gate, list-membership seed/resume path, and property-changed snapshot diff are all logically sound. The new selector API routes use the standard auth pattern correctly. The only finding is a minor placement of the count pagination parameter in a POST endpoint URL query string rather than its request body.

apps/sim/app/api/tools/hubspot/lists/route.ts — the count pagination parameter may need to move from the URL query string into the POST request body.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Cron as Cron (every minute)
    participant Poll as hubspotPollingHandler
    participant HS as HubSpot CRM API
    participant DB as providerConfig (DB)
    participant WF as processPolledWebhookEvent

    Cron->>Poll: pollWebhook(ctx)
    Poll->>DB: read config (watermarkMs, lastSeenObjectId, snapshot)

    alt "objectType == list_membership"
        Poll->>HS: "GET /lists/{id}/memberships/join-order?after=cursor"
        HS-->>Poll: results + paging.next.after
        loop seed phase
            Poll->>DB: update cursor, no emit
        end
        loop normal phase
            Poll->>WF: processPolledWebhookEvent(payload)
            WF-->>Poll: success/failure
        end
        Poll->>DB: "advance cursor only if failedCount == 0"
    else search-based
        alt first poll
            Poll->>DB: "seed watermarkMs = now"
        else subsequent poll
            Poll->>HS: "POST /objects/{type}/search (GroupA OR GroupB)"
            HS-->>Poll: results[]
            Note over Poll: client-sort (ts ASC, id ASC), slice to maxRecords
            loop each record
                alt property_changed and value unchanged
                    Poll->>Poll: skip, update snapshot LRU
                else
                    Poll->>WF: executeWithIdempotency
                    WF-->>Poll: success/throw
                    alt failure
                        Poll->>Poll: "cursorFrozen = true"
                    end
                end
                Poll->>Poll: advance cursor only if success and not frozen
            end
            Poll->>DB: persist watermark + snapshot
            alt all failed
                Poll->>DB: markWebhookFailed
            else
                Poll->>DB: markWebhookSuccess
            end
        end
    end

_{Reviews (4): Last reviewed commit: "fix(hubspot): Map-backed property snapsh..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review